System and method for remotely initializing a RF transaction

ABSTRACT

The present invention relates to a process for providing a RF module configured to convert a nontraditional transaction device for traditional transaction completion. The RF module is placed in physical and logical communication with a microprocessor of a nontraditional transaction device for receiving a personalization file to enable the RF module to complete RF transactions. In an exemplary embodiment, the microprocessor is configured to receive the personalization file from a mobile device account provider subsequent to an end user establishing communication with the device account provider and notifying the provider that a RF module is to be personalized. The mobile device account provider may receive the personalization file from a RF module account issuer and provide the personalization file to the RF module via the mobile device microprocessor. In another exemplary embodiment, the mobile device may include a USB interface for use in providing the personalization file to the RF module by establishing communications between the USB interface and the mobile device account provider or the RF module account provider as required.

CROSS-REFERENCE TO RELATED APPLICATIONS

This invention claims priority to and the benefits of U.S. ProvisionalApplication Ser. No. 60/512,297, filed Oct. 17, 2003. This invention isalso a continuation-in-part of, and claims priority to, U.S. applicationSer. No. 10/746,781, entitled “A SYSTEM AND METHOD FOR MANUFACTURING APUNCH-OUT RFID TRANSACTION DEVICE,” filed Dec. 24, 2003. This inventionis also a continuation-in-part of, and claims priority to, U.S. patentapplication Ser. No. 10/192,488, entitled “SYSTEM AND METHOD FOR PAYMENTUSING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESSTRANSACTIONS,” filed Jul. 9, 2002 (which itself claims priority to U.S.Provisional Patent Application No. 60/304,216, filed Jul. 10, 2001).

The invention is also a continuation-in-part of and claims priority, toU.S. patent application Ser. No. 10/340,352, entitled “SYSTEM AND METHODFOR INCENTING PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACTAND CONTACTLESS TRANSACTIONS,” filed Jan. 10, 2003 (which itself claimspriority to U.S. Provisional Patent Application No. 60/396,577, filedJul. 16, 2002).

The entire contents of each of these applications is hereby incorporatedby reference.

FIELD OF INVENTION

The present invention generally relates to transaction devices, and moreparticularly, to a system and method remotely configuring an RF modulefor RF transaction completion.

BACKGROUND OF INVENTION

For many years, personal checks, travelers checks, money orders,traditional currency and the like were the most popular means for payingfor goods or services. In recent years, however, transaction cards(e.g., credit cards, debit cards, smart cards, pre-paid cards, and thelike), have developed as a popular substitute for cash or personalchecks. The average consumer often prefers the transaction cards overtraditional currency since the transaction cards may be easily replacedby the card issuer if the user loses or misplaces the card or the cardis stolen.

As the number of issued transaction cards increases, so do the securityissues surrounding transaction card transactions. As a consequence, thetransaction card industry started to develop more sophisticatedtransaction cards which allowed for the reading, transmission, andauthorization of transaction card data, while lessening the elevatingsecurity concerns. One alternative transaction card that has gainedpopularity is the smart card. Smart cards are capable of transferringuser information during transaction completion without the user everhaving to lose physical control of the device. Thus, smart cards enhancethe security of the transactions by virtually eliminating the need forthe user to hand the card over to a merchant salesperson for transactioncompletion.

While smart cards enhanced some security surrounding transactiondevices, smart cards did little to address fraud issues associated witha lost or stolen transaction card. Because smart cards are manufacturedwith the same size dimensions as traditional transaction cards, the userdid little more to secure the smart card against loss than the user didto secure a traditional credit card. This revelation has led transactioncard providers to search for a suitable technology that encompassed theenhanced security given by smart cards and more. One such technology isradio frequency (RF) technology.

Like barcode and voice data entry, RF is a contactless informationacquisition technology. RF systems are wireless, and are usuallyextremely effective in hostile environments where conventionalacquisition methods fail. In general, RF technology permits a cardmanufacturer to provide for a dimensionally smaller transaction devicethan a smart card or traditional transaction card. RF technology,therefore, is better suited for securing against loss or theft. Forexample, the RF technology may be embodied in a form factor attachableto the account holder's person or to an often used (or often handled)personal article, such as a key chain, fob or tag. The RF transactiondevice may be attached to the personal article in an unobtrusive mannerbecause of its smaller size. As such, the user has increased securityagainst loss or theft, since the user handles the personal articlefrequently, permitting the user to repeatedly be reminded that the cardis present.

One of the more visible transaction devices which uses RFID technologyis found in the introduction of Exxon/Mobil's Speedpass® and Shell'sEasyPay® products, which are attachable to a user's key chain. Theseproducts use RFID transponders placed in a fob or tag of irregular shapewhich enables automatic identification of the user when the fob ispresented at a merchant Point of Sale (POS) device. Fob identificationdata is typically passed to a third party server database, where theidentification data is referenced to a customer (e.g., user) credit ordebit account for completion of a transaction.

By providing a RF transaction device (e.g., fob) as described above,transaction account providers are able to attract account users inincreasing numbers. The account users often prefer account providersthat offer the RF transaction device option because of the convenienceof use and the security using a RF transaction fob provides. Theincreased popularity of the RF fob has not gone unnoticed. Transactionaccount providers are now looking for various other devices in which toplace RF technology for convenient consumer use. These other devices maybe devices that the consumer uses more frequently than a traditionalcredit card or smart card.

One suitable device is the mobile telephone. Mobile telephones aretypically connected to a telephone network using a wireless connection.Because of their portability, users frequently carry mobile telephoneswith them throughout their day. Users often take their mobile telephoneswith them to the office, in the car, and wherever they might go. In thismanner, functions within the mobile telephone are available to the userthroughout the day. Moreover, the portability of mobile telephones,elevates mobile telephones to an important piece of equipment inconsumers' every day lives.

Another suitable device is the portable personal computer. As personalcomputers have increased in power and decreased in size, portablepersonal computers have become more useful and powerful. One smallerversion of the personal computer design that has proven useful and quitepopular is the so-called personal digital assistant (PDAs), such asNewton.RTM, by Apple Computer, Inc. In general, the average consumeruses the PDA to store telephone numbers and to manage the user'severyday schedule. However, because PDAs are highly programmable, PDAsmay be loaded with various software packages that provide otherfunctionality, such as wireless sending and receiving of data. As such,because of the increased popularity PDA use has become prevalent formanaging a user's everyday affairs.

Both mobile telephones and miniaturized portable personal computers,such as PDAs, suffer from one drawback in that they are generally notconfigured for use in any other way than originally intended.Electronics designers are constantly looking for ways to expand thefunctionality of the aforementioned mobile devices since the mobiledevices are gaining increasing popularity amongst consumers. Forexample, it would be desirable to configure the mobile devices fortransaction completion. Until then, the ordinary consumer is forced tocarry the mobile device and at least one transaction device, such as acredit card, debit card, loyalty card, or radio frequency transactiondevice (e.g., SPEEDPASS™ and EXPRESSPAY™) on his person. That is, theadvent of the technology era has increased a need to combine thefunctionality of the mobile devices with the transaction completioncapability of the transaction devices to limit the number of devicescarried by the consumer.

SUMMARY OF INVENTION

The present invention relates to a system and method for providing a RFoperable transaction device that may be used to convert any article to aRF transaction device. Specifically, the present invention relates to amethod of providing a RF module that may be manufactured usingconventional RF transaction card manufacturing machinery. The RF modulemay also be personalized using traditional personalizing machinery andprocesses.

It is, therefore, an object of the present invention to provide a RFoperable transaction device manufacturing system and method whichrequires little retrofitting of conventional transaction cardmanufacturing and personalization machinery.

In one embodiment, the present invention relates to a process forproducing a RF operable transaction device, having any one or morefeatures, such as a holographic foil, integrated circuit chip, silvermagnetic stripe with text on the magnetic stripe, opacity gradient,perforations included in the transparent device body for forming anoutline of a shape, and an “active thru” date on the front of thedevice.

In one aspect, the RF transaction device of the present invention mayuse RF technology to initiate and complete financial transactions. Inthat regard, the RF module included in the device may include one ormore RF operable transponders and antennas, which are typically includedduring the transaction device fabrication. The system in which the RFtransaction device may be used may include a RFID reader operable toprovide a RF interrogation signal for powering the RF module, receive aRF module RF signal including RF module account data, and provide RFmodule account data for transaction processing. The RFID reader mayinclude an RFID reader protocol/sequence controller in communicationwith one or more interrogators for providing an interrogation signal toa transponder of the RF module, a RF authentication circuit forauthenticating the signal received from the RF module, and a serial orparallel interface for interfacing with a point-of-interaction device.

The RFID reader may be configured to send a standing RF recognitionsignal which may be continuously or intermittently transmitted from theRFID reader via radio frequency (or electromagnetic) propagation. In oneinstance, the transaction device may be placed within proximity to theRFID reader such that the RF recognition signal may interrogate the RFmodule and initialize RF module identification or authorizationprocedures.

In another aspect of the invention, a RF module is provided which may beissued to a user in a transaction device transporter wherein the usermay remove the transaction device from the transporter for use with anyform factor. In one exemplary transaction device manufacturing method, aplurality of transporter and RF modules (called “transaction devicecombination” herein) are manufactured simultaneously on a single sheetusing conventional manufacturing machinery. Each of the plurality oftransaction device combinations is manufactured as a removable subpartthe sheet of the plurality of transaction device combinations, whereineach combination may be an independent operable RF transaction device,which is ISO/7810-1985 compliant in size. As such, the transactiondevice combination may be manufactured, stamped, and/or cut usingconventional manufacturing equipment.

The transaction device transporter, including the removable transactiondevice, is manufactured with at least one border of the transactiondevice transporter directly adjacent a border of the next adjacenttransporter, forming a sheet of conjoined transaction devicetransporters. In one embodiment, the sheet of transporters ismanufactured including RF operable transaction devices. In oneembodiment, the sheet is manufactured with RF operable transactiondevices including conventional RF data transmission circuitry.

Once the sheet of transaction device combinations is manufactured, thesheet may then be fed through a stamping device for imprinting anoutline of the transaction device (e.g., key fob) within a singletransporter. The outline of the transaction device is imprinted in thetransporter with sufficient depth such that the transaction device andthe RF module may be removed from the transporter with minimum physicalforce. The removable transaction device outline is imprinted such thatthe transaction device RF circuitry (called “RF module” herein), isincluded within the shape stamped (or imprinted) into the transactiondevice transporter, with at least a single imprint included within thetransporter's borders. As such, the outline of the transaction devicemay typically serve as the shape of the transaction device which may beremoved from the transporter.

The sheet may then be cut along the borders of the transaction devicetransporter into conventional transaction card dimensions, such as, forexample, the ISO/IEC 7812 standardized card dimensions noted above. Inone embodiment, the sheet is cut such that the transaction card shapedtransaction device combination resulting from the cutting processincludes the removable transaction device. The resulting transactiondevice combination may then be delivered to a transaction device user,who may remove (“punch-out”) the removable transaction device from thetransaction device transporter by, for example, applying minimalphysical force along lines (e.g., alignment lines) defining the shape ofthe transaction device imprinted on the transporter. Once removed, theRF transaction device may be used to complete a RF transaction since thetransaction device includes the RF module. Further, the outline of theimprinting may serve to define the shape of the transaction device. Thetransaction device manufacturer may predetermine the shape of thetransaction device and imprint the predetermined shape in thetransporter.

In another embodiment, the transaction device may not be removed fromthe transporter. Instead, the transaction device combination may be leftintact. The combination may be used to complete a RF transaction sincethe RF module is included in the transaction device (which is includedin the transaction device combination). In this way, the transactiondevice combination may be used in similar manner as a conventional RFtransaction device to complete a transaction. That is, a user mayposition the transaction device combination in proximity to a RFIDreader. The RF module may then provide transaction device accountinformation (e.g., account number, user identifier, device identifier)to the reader, which may forward the information to a merchant system orPOS for transaction completion.

Alternatively, the transaction device combination may be equipped with atraditional magnetic stripe, which is ordinarily ISO/IEC 7800 et al.,compliant. The magnetic stripe may include user account data which maybe provided to a conventional magnetic stripe reader for completing atransaction using traditional magnetic stripe data processing methods.Thus, the user may use the transporter and RF transaction device insimilar manner as a traditional credit card or debit card, and the like.

In another exemplary embodiment, the transaction card body is cut andthe transaction device outline is imprinted simultaneously. In thisinstance, the card manufacturer may utilize a cutting machine configuredto imprint an outline of the removable transaction device when thecutting of the transporter is performed. In this way, only one machineaction is necessary to cut the transporter body and imprint theremovable transaction device outline.

In yet another exemplary embodiment, the transaction device includes aRF module completely contained within the transaction device outlineformed by the imprinting action. The transaction device may be formed orshaped using any desired outline. For example, a suitable outline suchas an irregularly shaped key fob outline may be pressed (e.g.,imprinted) within the perimeter of each of the plurality of transactiondevice transporters. The transaction device outline may be pressed orimprinted into the transporter such that the RF module is containedwithin the transaction device outline. The transaction device may thenbe “punched out” of (“removed from”) the transporter by placing minimalphysical force at the transaction device outline, such that theresulting RF transaction device is shaped in the transaction deviceoutline provided.

In yet another exemplary embodiment of the invention, the transactiondevice manufacturer may manufacture a transaction device sheet includingthe RF module wherein the sheet may be cut in the traditional creditcard ISO/IEC 7800 et al., compliant shapes and the transaction device iscut in any shape as desired for a RF transaction device (e.g., teardropfob shaped). In this way, a transaction device manufacturer may formboth transaction cards and irregularly shaped RF transaction devices onthe same sheet simply by designating the proper design or shape to bemade.

In still another aspect, the invention includes a means for securing thetransaction device to a user's person or to a user's frequently usedpersonal apparatus. For example, in one particular embodiment, theoutline of the transaction device may be shaped to include an opening oraperture for securing the transaction device to, for example, a chain,key ring, ring, watch, rope, or the like. The key ring or chain, forexample, may be inserted through the opening to secure the paymentdevice to the chain or key ring to guard against the payment devicebeing easily lost or stolen.

In another exemplary embodiment, the RF module may be removed from thetransaction device for use in completing a transaction independently ofthe transaction device or the transporter. The outline of the module mayadditionally be pressed inside a transaction device outline as well,although not required. In this instance, an outline of the RF module maybe imprinted on the transaction device transporter wherein the module ispositioned inside the transporter outline. The RF module outline may beimprinted or pressed into the transporter at sufficient depth to permitthe module to be easily removed, in similar manner as discussed with thetransaction device. The module may be removed from the transporter usingany of the methods described herein.

Once removed, the RF module may be secured to a mobile device such as amobile telephone, PDA or the like, for converting the mobile device foruse as a RF transaction device. The module may be secured externally tothe mobile device housing using an independent portable carrier, anadhesive or other attachment method. The portable carrier may beattachable to the mobile device and may be configured to encase aportion of the RF module and lock the module in place to the mobiledevice body.

In yet another exemplary embodiment, the RF module may be placed inphysical and logical communication with the internal functionalcomponents of the mobile device (e.g., mobile device circuitry). The RFmodule may include electrical connections for communicating with themobile device microprocessor. In this way, the mobile device may be usedto power the RF module, transfer data between the mobile devicemicroprocessor, mobile account issuer, and RF module account issuer, andprovide secondary identification means for the RF transactionauthentication process, or to personalize the RF module where necessary.Additionally, the RF module may be configured to transmit information toa mobile device universal bus (USB) connector for transmitting theinformation to an account issuer or merchant system for transactionprocessing. The mobile device USB connector may permit the RF module tocommunicate with an issuer or merchant provided kiosk, or to atransaction processing network for transaction completion.

Additional features and advantages of the present invention aredescribed in, and will be apparent from, the detailed description of thepresent exemplary embodiments and from the drawings.

BRIEF DESCRIPTION OF DRAWINGS

A more complete understanding of the present invention may be derived byreferring to the detailed description and claims when considered inconnection with the Figures, where like reference numbers refer tosimilar elements throughout the Figures, and:

FIG. 1 illustrates an exemplary RF transaction device system inaccordance with an exemplary embodiment of the present invention;

FIG. 2 illustrates an exemplary prior art transaction card in accordancewith an exemplary embodiment of the present invention;

FIG. 3 illustrates an exemplary sheet of plurality of transaction cardsin accordance with an exemplary embodiment of the present invention;

FIG. 4 illustrates an exploded view of an exemplary sheet of a pluralityof transaction cards including a RF circuitry sheet in accordance withan exemplary embodiment of the present invention;

FIG. 5 depicts the front surface of an exemplary RF transaction devicein accordance with an exemplary embodiment of the present invention;

FIG. 6 shows an exemplary RF module in accordance with an exemplaryembodiment of the present invention;

FIG. 7 depicts the front surface of an exemplary RF transaction devicecombination in accordance with an exemplary embodiment of the presentinvention;

FIG. 8 illustrates an overview of an exemplary method for providing atransaction device to an end user in accordance with exemplaryembodiments of the present invention;

FIG. 9 shows an exemplary sheet of a plurality of cojoined transactiondevice combination each including a RF transaction device, therein, inaccordance with an exemplary embodiment of the present invention;

FIG. 10 is an exemplary detailed flowchart of an exemplary method forproviding a transaction device to an end user in accordance withexemplary embodiments of the present invention;

FIG. 11 depicts an exemplary transporter and RF module combination inaccordance with the present invention;

FIG. 12 depicts an exemplary RF module removed from a transporter inaccordance with the present invention;

FIG. 13 depicts an exemplary embodiment of a suitable frequently usedportable form factor comprising a recess for including a RF module inaccordance with the present invention;

FIG. 14 depicts an exemplary RF module carrier in accordance with thepresent invention;

FIG. 15 depicts a transaction device combination including a magneticstripe in accordance with exemplary embodiments of the presentinvention;

FIG. 16 depicts a transaction device combination with the transactiondevice removed in accordance with exemplary embodiments of the presentinvention;

FIG. 17 depicts an exemplary RF module in physical and logicalcommunication with an exemplary mobile device microprocessor inaccordance with exemplary embodiments of the present invention;

FIG. 18 depicts an exemplary RF module including electrical contacts foruse in a (SIM) slot for converting the mobile device to a RF transactiondevice in accordance with exemplary embodiments of the presentinvention;

FIG. 19 depicts an exemplary mobile device including electrical contactsfor inclusion of a subscriber identity module (SIM) in accordance withexemplary embodiments of the present invention;

FIG. 20 illustrates an exemplary method for processing a transaction inaccordance with exemplary embodiments of the present invention;

FIG. 21 depicts the functional components of an exemplary RFID readeruseful with the present invention;

FIG. 22 depicts an exemplary mutual authentication process in accordancewith the present invention;

FIG. 23 depicts an exemplary personalization system useful with thepresent invention;

FIG. 24 illustrates an exemplary personalization method useful with thepresent invention; and

FIG. 25 illustrates an exemplary personalization method useful with thepresent invention.

DETAILED DESCRIPTION

The present invention relates to contactless transaction devices andmethods of making and using the same. Specifically, the presentinvention relates to a system and method for providing a RF transactiondevice using conventional transaction card manufacturing procedures. Thepresent invention addresses the shortcomings in the prior art byproviding a cost effective method for manufacturing irregular shaped RFtransaction devices.

The present invention may be described herein in terms of functionalblock components, screen shots, optional selections and variousprocessing steps. Such functional blocks may be realized by any numberof hardware and/or software components configured to perform tospecified functions. For example, the present invention may employvarious integrated circuit components (e.g., memory elements, processingelements, logic elements, look-up tables, and the like), which may carryout a variety of functions under the control of one or moremicroprocessors or other control devices. Similarly, the softwareelements of the present invention may be implemented with anyprogramming or scripting language such as C, C++, Java, COBOL,assembler, PERL, extensible markup language (XML), JavaCard and MULTOSwith the various algorithms being implemented with any combination ofdata structures, objects, processes, routines or other programmingelements. Further, it should be noted that the present invention mayemploy any number of conventional techniques for data transmission,signaling, data processing, network control, and the like. For a basicintroduction on cryptography, review a text written by Bruce Schneierentitled “Applied Cryptography: Protocols, Algorithms, and Source Codein C,” published by John Wiley & Sons (second edition, 1996), hereinincorporated by reference.

In addition, many applications of the present invention could beformulated. The exemplary network disclosed herein may include anysystem for exchanging data or transacting business, such as theinternet, an intranet, an extranet, WAN, LAN, satellite communications,and/or the like. It is noted that the network may be implemented asother types of networks, such as an interactive television network(ITN).

FIG. 1 illustrates an exemplary Radio Frequency (RF) transaction devicesystem 100 for use with the present invention, wherein exemplarycomponents for use in completing a contactless transaction are depicted.In general, the operation of system 100 may begin when a contactlesstransaction device 102 is presented for payment. The device may bepresented for payment by, for example, waiving the device 102 inproximity to a RFID reader 104. The RFID reader 104 provides aninterrogation signal for powering the device 102 and the transactiondevice 102 is positioned in such proximity to the reader 104 that thedevice 102 may be positioned to be in communication with the transactiondevice 102 via RF transmission of the interrogation signal. Theinterrogating signal may power the contactless transaction device 102thereby initiating operation of the device 102. The contactlesstransaction device 102 may provide a transponder identifier and/oraccount identifier to the RFID reader 104, via RF transmissions and thereader 104 may further provide the identifier to the merchant system 130POS device 110 for transaction completion. Details for the operation ofan exemplary RF transponder system for transaction completion is foundin U.S. patent application Ser. No. 10/192,488, entitled “SYSTEM ANDMETHOD FOR PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT ANDCONTACTLESS TRANSACTIONS,” and its progeny which is hereby incorporatedby reference.

Although the point-of-interaction device is described herein withrespect to a merchant point-of-sale (POS) device, the invention is notto be so limited. Indeed, a merchant POS device is used herein by way ofexample, and the point-of-interaction device may be any device capableof receiving device account data. In this regard, the POS may be anypoint-of-interaction device or transaction acceptance device enablingthe user to complete a transaction using an RF responsive transponder.

The RFID reader 104 may be configured to communicate using a RF internalantenna 106. Alternatively, RFID reader 104 may include an externalantenna 108 where the external antenna 108 may be made remote to theRFID reader 104 using a suitable cable and/or data link. RFID reader 104may be further in communication with a transaction completion system(e.g., merchant system 130) via a data link. In one exemplary embodimentthe transaction completion system may include POS device 110 incommunication with a RFID reader 104 (via a data link), and a customerinterface 118 in communication with the POS device 110. The POS 112 maybe in further communication with an account issuer system (not shown)via a network 112 which may be provided the account number and anytransaction identifying information (e.g., time, duty, cost oftransaction, item negotiated) for transaction completion.

The terms “Internet” or “network” as used herein, may refer to theInternet, any replacement, competitor or successor to the Internet, orany public or private inter-network, intranet or extranet that is basedupon open or proprietary protocols. Specific information related to theprotocols, standards, and application software utilized in connectionwith the Internet may not be discussed herein. For further informationregarding such details, see, for example, DILIP NAIK, INTERNET STANDARDSAND PROTOCOLS (1998); JAVA 2 COMPLETE, various authors, (Sybex 1999);DEBORAH RAY AND ERIC RAY, MASTERING HTML 4.0 (1997); LOSHIN, TCP/IPCLEARLY EXPLAINED (1997). All of these texts are hereby incorporated byreference.

By being in “communication,” what is described may be that a signal maytravel to/from one component of the invention to another. The componentsmay be directly connected to each other or may be connected through oneor more other devices or components. The various coupling components forthe devices can include but are not limited to the Internet, a wirelessnetwork, a conventional wire cable, an optical cable or connectionthrough air, water, or any other medium that conducts signals, and anyother coupling device or medium.

Where required, the system user may interact with the system to completea transaction via any input device or user interface 118, such as, akeypad, keyboard, mouse, kiosk, personal digital assistant, handheldcomputer (e.g., Palm Pilot®, Blueberry®), cellular phone and/or thelike. Similarly, the invention could be used in conjunction with anytype of personal computer, network computer, work station, minicomputer,mainframe, or the like running any operating system such as any versionof Windows, Windows NT, Windows 2000, Windows 98, Windows 95, MacOS,OS/2, BeOS, Linux, UNIX, Solaris or the like. Moreover, although theinvention may frequently be described as being implemented with TCP/IPcommunications protocol, it should be understood that the inventioncould also be implemented using SNA, IPX, Appletalk, IPte, NetBIOS, OSIor any number of communications protocols. Moreover, the systemcontemplates the use, sale, or distribution of any goods, services orinformation over any network having similar functionality describedherein.

A variety of conventional communications media and protocols may be usedfor the data links. For example, data links may be an Internet ServiceProvider (ISP) configured to facilitate communications over a local loopas is typically used in connection with standard modem communication,cable modem, dish networks, ISDN, Digital Subscriber Lines (DSL), or anywireless communication media. In addition, the merchant system 130including the POS device 110 and host network 112 may reside on a localarea network which interfaces to a remote network (not shown) for remoteauthorization of an intended transaction. The merchant system 130 maycommunicate with the remote network via a leased line, such as a T1, D3line, or the like. In addition, the merchant system 130, including thePOS 110 and host network 112, may reside on a local area network, whichinterfaces with a remote network (not shown) for remote transactionauthorization. Such communications lines are described in a variety oftexts, such as, “Understanding Data Communications,” by Gilbert Held,which is incorporated herein by reference.

A device account identifier or account number, as used herein, mayinclude any identifier for a transaction device which may be correlatedto a user transaction account (e.g., credit, charge debit, checking,savings, reward, loyalty, or the like) maintained by a transactionaccount provider (e.g., payment authorization center). A typicaltransaction account identifier (e.g., account number) may be correlatedto a credit or debit account, loyalty account, or rewards accountmaintained and serviced by such entities as American Express, Visaand/or MasterCard or the like.

In general, the transaction devices 102 which use the above RFtransmission process may take any form. The RF module 20 may be includedin RF transaction device 102 for use in completing a RF transaction. Anytransaction device discussed herein, excluding the RF module 20, mayalso be termed a mobile device 102, wherein the mobile device isconfigured to accept the RF module 20. In an exemplary embodiment, themobile device 102 includes a microprocessor for controlling the mobiledevice 102 functional components as discussed below. In one embodiment,the mobile device 102 is one whose ordinary function is not forfinancial transaction completion or the completion of a transactionusing loyalty or rewards points, etc. In this instance, the mobiledevice may be termed a “non-traditional transaction device” herein.

To facilitate understanding of this invention, FIG. 5 illustrates a RFtransaction device 102 shaped as a teardrop shaped transaction device102, although other shapes are contemplated. FIG. 5 shows an exemplaryteardrop shaped RF transaction device 102, including RF module 20 forconducting a RF transaction.

The RF transaction device 102 (described more fully below) may come inmany different shapes. Because a typical card manufacturer may provideboth traditional credit card shaped transaction cards and irregularlyshaped RF transaction devices, the manufacturer must have propermachinery for cutting sheets of the devices into the appropriate devicesize. The present invention provides a system and method for forming theirregularly shaped transaction devices, which utilizes conventionaldimensional standards for transaction cards (e.g., credit cards, smartcards, etc.) irrespective of the RF transaction device shape. This, inturn, allows the manufacturer to manufacture irregularly shapedtransaction devices using conventional card manufacturing machinery,with little retrofitting. The invention allows for a manufacturer to usecoextensive transaction card and RF transaction device manufacturingprocesses which produce both transaction devices simultaneously orindividually. The process is termed coextensive since identical materiallayers and/or circuitry may be used whether the card manufacturerdesires to cut transaction cards or RF transaction devices.

FIG. 2 depicts the dimensional relationship of an exemplary transactioncard 1. Transaction card 1 is shown with dimensional characteristicswhich conform to the ISO card size standard, typically ISO/IEC 7800 etal. Generally, transaction card 1 is about 2″×3.5″.

Manufacturers of transaction cards 1 take advantage of mass productiontechniques when manufacturing transaction cards. Instead of producingthe cards 1 individually, the cards 1 are produced en masse in sheets200 which are then cut into the appropriate individual size. FIG. 3 is adepiction of an exemplary sheet 200 of a plurality of transaction cards1, which may be manufactured using a conventional transaction cardmanufacturing process.

Sheet 200 may be prepared using any conventional method of manufacturinga sheet of multiple transaction devices 1. The present inventionmodifies conventional methods by including perforation, impressing andRF circuitry as discussed below. The following description is anexemplary method of manufacturing sheet 200 according to the invention.The description is offered to facilitate a understanding of theinvention and not by way of limitation.

In the exemplary embodiment shown, sheet 200 may be formed usingmultiple material layers. FIG. 4 illustrates an exploded view of anexemplary sheet 200, which may be used with the present invention. Sheet200 includes a front material layer 10 and back material layer 12consisting of a plastic substrate such as, for example, clear core PVC.One skilled in the art will appreciate that layers 10 and 12 of card 1may be any suitable transparent, translucent and/or opaque material suchas, for example, plastic, glass, acrylic and/or any combination thereof.Each material layer 10, 12 is substantially identical and is preferablyabout 3″×4″ (622 mm×548 mm) and about 0.005–0.350 inches, or morepreferably 0.01–0.15 inches or 13.5 mil thick.

The fabrication of the individual card sheets 200 may include eitherdirect layout (9 layers) of film or the use of a sub-assembly (5layers). An exemplary sub-assembly layer 21 may consist of 5 layers offilm with room temperature tack adhesive applied over thermoset andthermoplastic adhesives. The resulting cards comprise (from the cardfront towards the card back) 2.0 mil outer laminate (PVC,polyvinylchloride) including having a holographic foil, embossedsurface, chip and other indicia on its surface, 9.0 mil printed PVC corewith print side out (card front), 2.0 mil PVC adhesive, 1.7 mil PET GS(extrusion coated polyethyleneterephthalate—gluable/stampable)manufactured by D&K (525 Crossen, Elk Grove Village, Ill. 60007), 2.0mil PET IR blocking film, 1.7 mil PET GS, 2.0 mil PET adhesive, 9.0 milprinted PVC core with the print side out (card back), and 2.0 mil outerback laminate with a signature panel, applied magnetic stripe and otherindicia. Optimally, the PET IR blocking film is fabricated in the middleof the layers to balance the card and minimize warping of the resultingcard product.

After eventually combining the sheets, by preferably adhering the frontlayer 10 on top of the back sheet 12, the total thickness of thetransaction card 1, including the subassembly sheet 21, is about 0.032in. (32 mil.), which is within the ISO thickness standard for smartcards. In one embodiment, the subassembly sheet 21 may be formedincluding RF module 20, which may be of sufficient thickness to maintainthe smart card standard thickness. Alternatively, the RF module 20 maybe embedded in the sheet 12 or card 1 via a suitable conventionalmilling process. Because the RF module 20 may eventually embedded intothe surface of the substrate or the subassembly 21 as described morefully below, the module 20 does not affect the thickness of the overallcard 1. Moreover, the about 3′×4′ sheets include predefined alignmentmarkings which define the boundaries of the individual cards 1 to be cutfrom the sheet. Each exemplary sheet yields over 50 transaction cards(typically 56 cards), wherein each card 1 is within the ISO card sizestandard, namely about 2″×3.5″.

In an exemplary embodiment, certain compounds are printed over thesurface of sheets 10 and 12. The compounds may be printed in accordancewith accepted ISO standards. One skilled in the art will appreciate thatthe printing of the text 30 and logo 50, and optically recognizable inkmay be applied to any surface of card 1 such as, for example, the front10 face (front material layer 10), the rear 12 face (rear material layer12), the inside or outside surface of either face, between the twosheets of base material and/or a combination thereof. Moreover, anysuitable printing, scoring, imprinting, marking or like method is withinthe scope of the present invention.

The text 30 and logo 50 are printed on the outside surface of eachmaterial layer 10, 12 by a known printing process, such as an offsetprinting process, which provides a thinner ink coverage, but clearertext. More particularly, with respect to offset printing, the artwork isduplicated onto a metal plate and the metal plate is placed onto anoffset press printing machine which can print up to four colors during asingle run. The offset printed text may include, for example, acorporate name, a copyright/trademark/patent notice, a batch codenumber, an “active thru” date, contact telephone numbers, legalstatements and/or the like. The exemplary offset text may be printed in4DBC in opaque white ink or a special mix of Pantone Cool Gray 11 calledUV AMX Gray. In one exemplary embodiment, the offset printed text isprinted directly on the RF module 20, such that the text is visible onthe module 20 through casual inspection.

A laminate material layer 15 is applied to the back layer 12 of card 1.In one preferred embodiment, the laminate layer 15 includes rows of ISOcompliant magnetic stripes 40, wherein each magnetic stripe 40corresponds to an individual card 1. The magnetic stripe 40 may extendalong one length of the card 1 and is applied to the back surface 12.The magnetic stripe 40 may be any width, length, shape, and placed onany location on card 1. In an exemplary embodiment, the magnetic stripe40 is applied to the outer laminate layer 15 using a tape layer machinewhich bonds the cold peel magnetic stripe 40 to the outer laminate 15when it is in a rolled position (not shown). The laminate 15 roll with arolling hot die and at suitable pressure. The roll is then cut intolayers 10, 12 before the card layers are assembled.

After the desired printing is complete and the magnetic stripe applied,the front 10 and back 12 material layers are placed together, and thelayers are preferably adhered together by any suitable adhering process,such as a suitable adhesive. One skilled in the art will appreciatethat, instead of printing on two material layers and combining the twomaterial layers, a single plastic material layer can be used, whereinthe single material layer is printed on one side, then the same materiallayer is re-sent through the printer for printing on the opposite side.

In the present invention, after adhering the layers together, a layer oflamination (not shown), approximately the same dimensions as the plasticsheets, namely 3′×4′, may be applied over the front 10 and back 12 ofcard 1. After the laminate is applied over the front 10 and back 12 ofthe combined plastic material layers, card 1 layers are suitablycompressed at a suitable pressure and heated at about 300 degrees, at apressure of between 90–700 psi, with a suitable dwell time to create asingle card 1 device. The aforementioned card fabrication can becompleted by, for example, Oberthur Card Systems, 15 James Hance Court,Exton, Pa.

In an exemplary embodiment, the card layers 10 and 12 are fused togetherin a lamination process using heat and pressure. During the hot pressphase, the press is heated to about 300 F. degrees and the pressurebuilds to about 1000 psi and holds for about 90 seconds. The pressurethen ramps up to about 350 psi over an about 30-second period and holdsfor 16 minutes at the same temperature, namely 300° F. degrees. Thesheet 200 is then transferred to a cold press which is at about 57° F.degrees. The pressure builds to about 400 psi and is held for about 16minutes as chilled water of about 57° F. degrees is circulated in theplates. The cold press then unloads the sheet 200.

In one exemplary manufacturing embodiment, the cards 1 may includeinternal circuitry for use in completing contactless transactions. Forexample, card 1 may include a RF module 20 included in the card body andpreferably may be included in subassembly sheet 21. The RF module 20 ispreferably positioned substantially central to the card body but may bepositioned at any desired location therein. The RF module 20 may beincluded interposed between front surface material layer 10 and backsurface material layer 20 during fabrication of the sheet 200.Specifically, the module 20 may be included interposed between at leasttwo layers of the subassembly sheet 20. Alternatively, after lamination,the RF module 20 may be included within an individual card 1 within aspace created by milling the card body and providing room for theinsertion of the RF module 20. As such, upon including the RF module 20,sheet 200 will comprise a plurality of RF operable transaction cards 1wherein each transaction card 1 includes a RF module 20. Traditionalmethods for including RF module 20 in transaction devices 1 are wellknown, and are intended to be within the scope of the invention.

FIG. 6 illustrates a block diagram of the many functional components ofan exemplary RF module 20 in accordance with the present invention.Module 20 may include any conventional RF circuitry capable ofcommunicating via Radio Frequency transmission. A suitable module 20 maybe presented by the user to facilitate an exchange of funds or points,etc., for receipt of goods or services.

RF module 20 may include an antenna 204 for receiving an interrogationsignal from RFID reader 104 via antenna 106 (or alternatively, viaexternal antenna 108). Module antenna 204 may be in communication with atransponder 214. In one exemplary embodiment, transponder 214 may be a13.56 MHz transponder compliant with the ISO/IEC 14443 standard, andantenna 204 may be of the 13 MHz variety. The transponder 214 may be incommunication with a transponder compatible modulator/demodulator 206configured to receive the signal from transponder 214 and configured tomodulate the signal into a format readable by any later connectedcircuitry. Further, modulator/demodulator 206 may be configured toformat (e.g., demodulate) a signal received from the later connectedcircuitry in a format compatible with transponder 214 for transmittingto RFID reader 104 via antenna 204. For example, where transponder 114is of the 13.56 MHz variety, modulator/demodulator 206 may be ISO/IEC14443-2 compliant.

Modulator/demodulator 206 may be coupled to a protocol/sequencecontroller 208 for facilitating control of the authentication of thesignal provided by RFID reader 104, and for facilitating control of thesending of the module 20 account number. In this regard,protocol/sequence controller 208 may be any suitable digital or logicdriven circuitry capable of facilitating determination of the sequenceof operation for the module 20 inner-circuitry. For example,protocol/sequence controller 208 may be configured to determine whetherthe signal provided by the RFID reader 104 is authenticated, and therebyproviding to the RFID reader 104 the account number stored on module 20.

To authenticate the signal, the protocol/sequence controller 208 may befurther in communication with authentication circuitry 210 forfacilitating authentication of the signal provided by RFID reader 104.Authentication circuitry may be further in communication with anon-volatile secure memory database 212. Secure memory database 212 maybe any suitable elementary file system such as that defined by ISO/IEC7816-4 or any other elementary file system allowing a lookup of data tobe interpreted by the application on the chip. Database 212 may be anytype of database, such as relational, hierarchical, object-oriented,and/or the like. Common database products that may be used to implementthe databases include DB2 by IBM (White Plains, N.Y.), any of thedatabase products available from Oracle Corporation (Redwood Shores,Calif.), Microsoft Access or MSSQL by Microsoft Corporation (Redmond,Wash.), or any other database product. Database 212 may be organized inany suitable manner, including as data tables or lookup tables.Association of certain data may be accomplished through any dataassociation technique known and practiced in the art. For example, theassociation may be accomplished either manually or automatically.Automatic association techniques may include, for example, a databasesearch, a database merge, GREP, AGREP, SQL, and/or the like. Theassociation step may be accomplished by a database merge function, forexample, using a “key field” in each of the manufacturer and retailerdata tables. A “key field” partitions the database according to thehigh-level class of objects defined by the key field. For example, acertain class may be designated as a key field in both the first datatable and the second data table, and the two data tables may then bemerged on the basis of the class data in the key field. In thisembodiment, the data corresponding to the key field in each of themerged data tables is preferably the same. However, data tables havingsimilar, though not identical, data in the key fields may also be mergedby using AGREP, for example.

The data received from the reader 104 or the database 212 may be used byprotocol/sequence controller 208 for data analysis and used formanagement and control purposes, as well as security purposes.Authentication circuitry 216 may authenticate the signal provided byRFID reader 104 by association of the RF signal to authentication keysstored on database 212. Authentication circuitry 216 may be in furthercommunication with an encryption circuitry 216 which may encrypt ordecrypt the reader 104 signal or the data (e.g., account number, useridentifier, device identifier, etc.) returned from database 212 prior totransmitting the data. Encryption circuitry 216 may use keys stored ondatabase 212 to perform encryption and/or decryption of signals sent toor from the RFID reader 104.

In addition, protocol/sequence controller 208 may be in communicationwith a database 212 for storing at least one of a module 20 accountdata, a unique module 20 identification code, user identification code,or transaction device identifier. Protocol/sequence controller 208 maybe configured to retrieve the account number from database 212 asdesired. Database 212 may be of the same configuration as database 212described above. The account data and/or unique device identificationcode stored on database 212 may be encrypted prior to storage. Thus,where protocol/sequence controller 208 retrieves the account data, andor unique transaction device identifier, or the like, from database 212,the data may be encrypted by the encryption circuit 216 when beingprovided to RFID reader 104. Further, the data stored on database 212may include, for example, an unencrypted unique module 20 identificationcode, a user identification ISO/IEC, Track 1 and 2 data, as well asspecific application applets. The data may additionally be stored in thedatabase 212 in Track 1/Track 2 format and may also be in Track 1/Track2 format when provided to the reader 104

In one exemplary embodiment, module 20 antenna 218 may be 134 KHz ratedconfigured to communicate with a 134 KHz transponder 214. In thisexemplary configuration, an ISO/IEC 14443-2 compliantmodulator/demodulator 206 may not be required. Further still, reader 104may also include an antenna 106, 108 and a transponder modulator whichis also ISO/IEC 1443-2 complaint to ensure successful RF communicationwith correspondent components at module 20.

In an exemplary operation, the module 20 is placed in proximity toreader 104 when the user wishes to conduct a transaction. The usersimply waves the module 20 at a certain distance from the RF-basedreader 104 until the reader 104 acknowledges that the informationcontained in the RF module 20 has been received. The RF-based reader 104then utilizes at least a portion of the information provided by module20 (such as, a user's account number associated with the transactiondevice) to complete the transaction. The reader 104 may receive theaccount information from the module 20 and verify the accountinformation authenticity prior to forwarding the account information tomerchant system 130. Alternatively, the reader 104 may forward theaccount information to a merchant system 130 (via the merchant systemPOS 110) which may provide the account information to a transactiondevice issuer system (via network 112) for transaction completion. Themerchant system 130 forwards the account information to an accountissuer system, which may complete the transaction under issuer definedbusiness as usual protocol. Exemplary transaction completion methods andtransaction device components are disclosed in the commonly owned U.S.patent application Ser. No. 10/192,488, entitled “SYSTEM AND METHOD FORPAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESSTRANSACTIONS,” filed on Jul. 9, 2002, incorporated herein in itsentirety.

With reference to FIG. 3, after the card sheet 200 is prepared,including the RF module 20, the sheets may be cut into individual cards1 by a known stamping process, including any necessary curing,burrowing, heating, cleaning and/or sealing of the edges. The individualtransaction cards 1 are about 2″×3.5″ and conform to ISO standards fortransaction card 1 shape and size. As used hereinafter, the transactioncard 1 is termed the transaction device “transporter,” since thetransaction device issuer may provide the RF module 20 to a user whenthe module 20 is still affixed to the transporter 1 as described below.

In an exemplary embodiment, the laminated sheet 200 of 56 transactiondevice transporters 1 (including the RF module) are suitably cut in halfon a guillotine device, resulting in two half-sheets of 28 transporters1 and module 20 combinations. The half-sheets may be loaded onto anyconventional card punch machine which aligns the sheets to a die (x andy axes) using predetermined alignment marks 202 visible to the optics ofthe machine. The half-sheets are then fed under a punch to punch out thedesired transporter device 1 and module 20 (called “transaction devicecombination”) shape. Particularly, a fixed distance feed is followed byanother optic sensor search to stop the feed at the preprinted alignmentmark, then the machine punches a row of four transaction devicecombinations out at one time, each punch being made along a preprintedalignment mark 202.

The preprinted alignment marks 202 indicate the perimeter boundaries ofeach transaction device transporter 1 to be cut from sheet 200. Toseparate each transaction device combination from the other, the cutsmay typically be made along the preprinted alignment marks 202. Ingeneral, the preprinted alignment marks 202 are included in the sheet200 as the writing is being added to the device material layers 10, 12.A typical sheet 200 may yield over 50 transaction device combinations(typically 56). In general, the shape of the transporter 1 is keptconsistent by using a cutting apparatus having a preformed cutting dyeformed in the desired shape. For example, the cutting dye may be formedin any shape, such as, for example, a traditional credit card shape asshown in FIG. 1. Alternatively, the shape is cut by using, for example,a laser or other cutting apparatus guided by any suitable preprintedalignment marks 202. The resulting individual transaction devicecombination may then be distributed for immediate activation and use.

Conventional methods of fabricating, manufacturing and cuttingtransaction devices, such as, credit cards, smart cards, RF key fobs arewell known. As such, one skilled in the art will understand themachinery and processes for fabricating, manufacturing, and/or cuttingas they are included in the scope of this invention. Indeed, in theinterest of brevity, conventional methods of fabricating, manufacturingand cutting transaction devices will not be discussed in detail herein.For instruction on manufacturing and fabricating a typical transactioncard, see U.S. patent application Ser. No. 10/092,681, entitled“TRANSACTION CARD,” filed Mar. 7, 2002, and incorporated herein in itsentirety.

While the foregoing describes an exemplary embodiment for thefabrication of transaction device combination, one skilled in the artwill appreciate that any suitable method for incorporating text 30,logos 50, a magnetic stripe 40, a signature field, holographic foil 15onto a substrate in accordance with accepted 160 standards, is withinthe scope of the present invention. Moreover, the holographic foil, RFmodule 20, logo 50, magnetic stripe 40, signature field or any othercompound may be included on the transporter 1 by any suitable means suchas, for example, heat, pressure, adhesive, grooved and/or anycombination thereof. In accordance with one embodiment, the text 30,logo 50, magnetic stripe 40, or holographic foil 15 may additionally beincluded in one surface use of the module 20 on a portion easilyviewable by casual inspection.

As noted, various card manufacturers are producing RF transactiondevices that are irregularly shaped. As such, the irregular shapedtransaction devices are typically cut using a cutting dye, or othermethod discussed above, which is designed to cut a sheet 200 into thedesired transaction device shape. Consequently, manufacturers must oftenretrofit their machinery to cut the irregular shape. Returning now toFIG. 5, a teardrop shaped RF transaction device (key fob) 500 is shown.To provide transaction devices of similar shape as device 102, a cardmanufacturer may typically use a cutting machine including a teardropshaped cutting dye, or a cutting means guided by the preprinted device102 alignment marks 502 (also shown in FIG. 7). As can be seen, the RFtransaction device 102 may include a logo 50.

In accordance with one aspect of the invention, a credit cardmanufacturer may provide an irregularly shaped RF transaction device 102using a manufacturing process that is coextensive with the manufacturingprocess used for traditional transaction card 1 shapes. That is, thetransaction devices 102 and transporters 1 may be manufactured, cut,perforated, or impressed without need to manufacture the devicesindependently of the transporter 1. FIG. 8 depicts an exemplary overviewof any transaction device combination manufacturing method according tothe invention. As shown in FIG. 8, and with continued reference to FIG.7, a transaction device sheet 200 (shown best in FIG. 9) including aplurality of conjoined RF transaction device combinations 1 is providedusing any of the manufacturing methods discussed herein (step 802). Thetransporter 1 may include an outline of irregularly shaped transactiondevices 102 defined by alignment marks 502. Alignment marks 502 mayordinarily be imprinted and pressed within the outline of thetransporter 1 defined by the preprinted alignment marks 202. The sheet200 may be prepared using conventional RF transaction device andtransaction card fabricating methods. The outline of the irregularshaped removable RF transaction device 102 which is shown as preprintedalignment marks 502 in FIG. 7, may be pressed into, and containedsubstantially inside, the preprinted alignment marks 202 of thetransporter 1 (step 804). The alignment marks 502 may be pressed intothe surface of the transponder and substantially therethrough. In oneembodiment, the alignment marks 502 are pressed into the surface of thetransporter 1 such that the transporter 1 and transaction device 102 arein physical contact. However, the irregular shaped removable RFtransaction device 102 may then be removed from (i.e., “punched out” of)the transporter 1 by using minimal physical force at preprintedalignment marks 202 (step 806). The resulting RF transaction device 102may then be used in completing a RF transaction under any merchant oraccount provider business as usual standards (step 808).

To assist in punching out or removing the transaction device 102, the RFtransaction device 102 preprinted alignment marks 502 may be pressedinto the body of transporter 1 defined by preprinted alignment marks202. As noted, the transporter 1 may be formed with one or more materiallayers, such as, for example, front layer 10, and back layer 12. Thepressing action may result in indentations, or perforations beingimpressed into or through one or more layers of the multilayertransaction device. However, the perforations or indentations may nottraverse completely through the card body. Instead, the perforations orindentations are impressed at such sufficient depth to permit thetransaction device 102 to be removed from the transporter 1 with theapplication of minimal physical force. Thus, the perforations orindentations are typically provided along the transaction device 102preprinted alignment marks 502 to facilitate the removal of thetransaction device 102 from the transporter body. In one exemplaryembodiment, the perforations and indentations, which may be used to formthe outline of the transaction device 102, may also be arranged to forman outline of a shape, a picture, a security enhancing visage, or thelike as desired by the manufacturer or system user. Suitable methods forproviding perforations are disclosed in U.S. patent application Ser. No.10/288,945, entitled “PERFORATED TRANSACTION CARD,” filed Nov. 6, 2002,incorporated herein by reference in its entirety.

FIG. 10 illustrates various exemplary embodiments of a method forproviding to a user RF transaction device 102 which may be removed froma transporter 1. In accordance with step 802, each exemplary embodimentbegins with the fabrication of a multilayer sheet 200 of a plurality ofconjoined transaction device combinations.

In accordance with one exemplary embodiment of the present invention,the transaction device 102 outline (lines 502) is impressed within theoutline of the transporter 1 drawn by alignment marks 202. For example,the preprinted sheet 200 of transaction device combinations is providedwith the transporter 1 alignment marks 202 preprinted on thecombination's front or rear surface 10, 12, and the transaction deviceoutline 502 (“alignment marks 502”) is impressed within the alignmentmarks 502 (step 804).

Once the impression of the transaction device 102 is made in thetransporter 1, the transaction device manufacturer may remove thetransaction device 102 from the transporter 1 and provide thetransaction device 102 to an end user. In one exemplary embodiment, thetransaction device 102 is removed from the transporter 1 by themanufacturer (step 808) prior to providing the transaction device 102 toa user for device activation and device usage (step 810). In this way,the transaction device 102 may be provided to a user independent of thetransporter 1. The user may use the transaction device 102 to complete atransaction by placing the transaction device 102 in proximity to thereader 104 as described above (step 830).

In an alternate embodiment of the invention, the RF transaction device102 is not removed by the manufacturer, but instead the RF transactiondevice 102 is removed from the transporter 1 by the end user (step 812).For example, a transaction device provider may provide a user with thetransaction device combination, including the transporter 1, and thetransaction device 102, which includes RF module 20 (step 814). The usermay then decide whether to remove the transaction device 102 from thetransporter 1, which may be removed at the user's leisure (step 816).Should the user remove the transaction device 102, the user mayadditionally decide whether to remove module 20 (step 818). The user mayremove the transaction device 102 to complete a transaction independentof the transporter 1 (step 830). The user may remove the transactiondevice 102 from transporter 1 by applying minimal physical force at thetransaction device outline 502. The transaction device 102 may beremoved manually or by cutting, tearing, or the like, (step 820). Theuser may use the transaction device 102 by placing the transactiondevice 102 in proximity to reader 104, as described above (step 830).The RF module 20 may then provide transaction device account informationto a RFID reader 104 for transaction completion.

The transaction device 102 may include an aperture 503, which may beformed by pressing the shape of the aperture 503 in the transporter 1along alignment lines 502, perforating the transaction device 102 shapein the transporter 1 using any conventional machinery or method asdescribed above. The aperture 503 may then be punched out or removed,wherein the portion of the transporter 1 within the aperture 503 isremoved leaving an opening therein. The transaction device 102 may thenbe secured to a user's person or often used personal article byinserting one end of a tether-like means (not shown) through aperture503 and securing the other end of the tether-like means to a transactiondevice 102 user person or often used personal article (e.g., keychain,fob chain, key ring, string, strap, belt, rope, etc.) which isordinarily easily portable (step 820). The user may then use thetransaction device 102 in similar manner as discussed above (step 830).

In another exemplary embodiment of the invention, user or transactiondevice manufacturer may remove the RF module 20 from the transporter 1to enable use of the module 20 to complete a transaction independent ofany other portion of the transporter 1 or the transaction device 102(step 822). In this instance, the transaction device issuer mayconfigure the stamping machinery to preprint alignment marks whichclosely mimic the shape of the module 20. As shown in FIG. 11, thetransporter 1 may include a square shaped module 20 including alignmentmarks 220. In similar manner as previously described, the issuer mayperforate the transporter 1 along the alignment marks 220 to facilitateeasy removal of the module 20 from the transporter 1 by the user or theissuer. The module 20 outline may be pressed substantially, but notcompletely, through transporter 1 body. In this way, the user may removemodule 20 from transporter 1 with minimal physical force (step 822). Theuser may then use the module 20 to complete a RF transaction bypositioning the module 20 in proximity to the reader 104 in similarmanner as was described with the transaction device 102 (step 830).

FIG. 12 shows the RF module 20 removed from the transporter 1. As shown,the module 20 may include the offset printed text described above (e.g.,logo, text 30, logo 50, active through date, telephone numbers, etc.),which is perceptible to the casual observer by visual inspection. Themodule 20, may be a self-contained device in that the module may be usedto complete transactions irrespective of the transporter 1. In exemplaryembodiment, the module 20 may be of sufficient size that it is easilypunched out or removed from the transporter 1. For example, the modulemay be 1×1 9/16″, although other suitable sizes are contemplated.

In one exemplary embodiment, the user may use the module 20 with anyportable form factor configured to secure the module 20 duringtransaction completion (step 824). In one embodiment, the form factor isembodied in an article frequently used by the module user. For example,the module 20 may be secured to any portable apparatus which may bemanually transported by the module 20 user, and which may be used tofacilitate manually presenting the module 20 to a RFID reader 104 fortransaction completion. A suitable portable apparatus may include meansfor securing the module 20 to the apparatus.

FIG. 13 shows an exemplary apparatus for securing and presenting themodule 20 for transaction completion which may be used in accordancewith the present invention. As shown, the apparatus may be anontraditional transaction device, such as, a conventional cellularphone 300 although any portable form factor including a microprocessormay be used. For example, the apparatus may be a personal digitalassistant (PDA), mini personal computer or the like. The cellular phone300 may include a recess 302 which may be configured to accept themodule 20 therein. The recess 302 may be included in one surface of thephone 300 at sufficient depth to substantially recess the RF module 20therein, to secure the module 20. The recess 302 may further beconfigured to hide the RF module 20 from view. The module 20 may therebybe inserted in the recess 302 and secured by any fastening means such asclips, molded clips and fittings, screws, glue, soldering or the like.The module 20, may be inserted into the recess 302 of the cellular phone300 prior to providing the phone 300 to the user. Alternatively, themodule 20 may be provided to the user in a transaction devicecombination, and the module may be removed from the transporter 1 andthe transaction device 102 and inserted in the recess 302 by the user.Further still, the module 20 may be provided to the user in thetransporter 1 or the transaction device 102, and the user may remove themodule 20 at the user's leisure.

In yet another exemplary embodiment, as shown in FIG. 14, a portablecarrier 400 may be provided to the user for securing the module 20during transaction completion. Carrier 400 may be of any desired shapebut may be of sufficient size to substantially enclose the module 20 inuse. The carrier 400 may be constructed of any durable or sturdymaterial such as metal, plastic, composite materials or the like. Thecarrier 400 may additionally be transparent or translucent to permitcasual viewing of the module 20 when the module 20 is secured therein.

For example, in the embodiment shown, carrier 400 is of similar shape asthe module 20 depicted in FIG. 12 (e.g., square), although the carrier400 may take any shape. In one embodiment, the carrier 400 may bedimensionally larger than the module 20 to ensure that the module may beenclosed therein although any carrier 400 shape or size may be used. Thecarrier 400 may include a recess 402 in which the module 20 may besnuggly fitted. The carrier 400 may include a first 404 and second 406carrier door. First 404 and second 406 carrier door may include therecess 402 included in one panel of each door. The recess 402 forms acavity when the doors 404, 406 are positioned one on the other. Themodule 20 may be secured in the cavity. The doors 404 and 406 may be incommunication along one side by hinges 408, which permit the doors 404,406 to be closed one on top of the other with the module 20 interposedin between. The doors 404, 406 may be secured one to the other by thehinges 408 and a suitable latch 410 configured to ensure that the doors404, 406 remain fastened one to the other and the module 20 remainsinside the carrier 400 during transaction completion.

Carrier 400 may further include an aperture 412 in at least one end ofthe door 404, 406. The aperture 412 may be used in similar manner aswith aperture 503 of FIG. 7. That is, the carrier 400 (which may includethe module 20) may be secured to a user's person or to an apparatus theuser frequently handles.

Alternatively, the carrier may be secured to the apparatus, such as cellphone 300 using any suitable attachment method. For example, the carrier400 including the module 20 may be fastened to the cell phone 300 usingany attachment means, such as for example, screws, rivets, bondingcompound, glue or especially made fastening construction operable tohold the carrier 400 in physical communication with the cell phone 1402.For example, one suitable attachment method may be the fastenerdescribed in U.S. Pat. No. 6,669,263, entitled “Attachment Device,”which issued December 30, 2003, to Asai, and U.S. Pat. No. 6,643,076,entitled “Attachment Device,” which issued Nov. 4, 2003, to Montage,hereby incorporated by reference.

Returning now to FIG. 8, in yet another exemplary method, the user maynot wish to remove the module 20 or the transaction device 102 from thetransporter 1 (steps 816 and 826). Instead, the user may wish to use thetransaction device combination to complete a transaction. That is, thetransaction device combination may be used with the module 20 and thetransporter 1 intact. FIG. 15 shows an exemplary depiction of atransaction device combination 600 in accordance with the presentinvention which may be used to complete a transaction. FIG. 15 depicts atransaction device combination 600 which includes a transporter 1 and aRF module 20. The combination 600 may further include the impression ofthe transaction device 102 although not required. For example, thetransporter 1 may include alignment lines 502 which trace a shape of atransaction device 102 including the RF module 20 the shape of which maybe formed from impressed alignment lines 220. Perforations may be madealong the alignment lines 502, 220 which trace at least one of the shapeof transaction device 1508 or the module 20.

The transporter 1 may be configured with a magnetic stripe 40 using anyconventional method for attaching magnetic stripes as is commonly known.The magnetic stripe 40 may be compliant to International StandardSetting Organization standards for the shape, location and the format ofthe data stored and retrieved from the magnetic stripe 40. The magneticstripe 40 may be configured to include account data (e.g., account,user, or transaction device identifier, code or number) stored thereonin Track 1/Track 2 ISO magnetic stripe standard format. As such, themagnetic stripe 40 may be configured to be readable by any conventionalmagnetic stripe reader as is found in the art. Consequently, the usermay use the transaction device combination 600 in similar manner as atraditional credit, debit, DDA, prepaid card, an the like. For example,the user may present the transaction device combination 600 to amagnetic stripe reader, which may retrieve the magnetic stripe 40 dataand forward the data to an account issuer for transaction completion.Conventional methods for completing a transaction are well known andwill not be repeated for brevity.

In one conventional construction of transaction device combination 600,the magnetic stripe 40 may be such that a portion of the alignment lines502, including the impressed outline of the transaction device 102 mayintersect the magnetic stripe 40, as shown in FIG. 15 at characterreference 608. In this way, the transaction device 102 outline overlapsthe magnetic stripe 40. As such, the transaction device 102 includingmodule 20 may be removed from the transporter 1 and a portion of themagnetic stripe 40 is removed therewith as shown in FIG. 16. In thisway, the user ensures that the transporter 1, including the remainingportion of the magnetic stripe 40, may not be used to completetransactions. This is true, since the magnetic stripe 40 will have aportion 606 of the magnetic stripe 40 removed when the device 102 isremoved, thereby making the magnetic stripe 40 inoperable fortransmitting complete magnetic stripe information. That portion 606 ofthe magnetic stripe 40, which is removed, may ordinarily be included asa portion of the transaction device 606 to ensure that the magneticstripe 40 may be disabled when the transaction device 102 is removed.Once removed, the transaction device 102, or the module 20 may be usedto complete a transaction in similar manner as was discussed above.

In still another exemplary embodiment, the removed RF module 20 may beplaced in physical and logical communication with a microprocessor of amobile device, such as for example, the cell phone 300 discussed withregard to FIG. 3. As shown in FIG. 17, the phone 300 may include amicroprocessor 1702 for controlling the operation of the phone 300. Themicroprocessor 1702 may be in communication with a mobile devicedatabase such as cell phone database 1704, for data storage andretrieval. For example, in the case of cell phone 300, database 1704 maystore personal contact information, calendars, pictures, or the like.The cell phone 300 may also include a modulator/demodulator 1706connected to the processor 1702 and a cell phone antenna 1708, fortransmitting signals received from the antenna 1708 to themicroprocessor 1702. RF module 20 may be placed in physical or logicalcommunication with the microprocessor 1702 using any conventionalcoupling methods for connecting electrical components.

In another exemplary method for placing the RF module 20 in physical andlogical communication with microprocessor 1702, the RF module 20 mayinclude contact points that are compatible with a mobile deviceexpansion card slot. Expansion cards are typically cards which containinstructions or data which the processor may use to enhance thefunctionality of an electronic device including a processor ormicroprocessor. One popular example of an expansion card is thesubscriber identity module (SIM).

Ordinarily, SIMs are configured to provide control applications to themobile device for controlling and increasing the device's functionality.Most SIMs are in the form of a chip card that establishes the subscriberrelationship with the mobile phone system operator. The chip cardtypically includes electrical contacts which mate with electricalcontacts of the mobile device for placing the chip card in communicationwith the mobile device processor. The mobile device mating contacts areusually included in a slot formed in the housing of the mobile devicefor receiving and securing the chip card thereto.

The SIMs are personalized with an IMSI, Ki, etc., prior to providing theSIMs to the mobile device user, at a “personalization” center run by themobile phone network operator. Important individual subscriber datasaved on the SIM facilitates the use of the mobile phone services. TheSIM contains the mobile subscriber identification (IMSI), the secretindividual subscriber key (Ki) an authentication algorithm (A3), aciphering key generating algorithm (A8), a personal identificationnumber (PIN) and other permanent and temporary data. The SIM contains atleast one microchip which holds information on the subscription andwhich, when the SIM card is inserted in a mobile terminal, is connectedthereto.

However, SIMs have a major drawback in that the SIMs ordinarily do notinfluence the behavior of the mobile device by managing presentation ofnew services (or software applications) to the user. To mitigate thatdrawback, GSM Recommendation 11.14 phase 2+ defines the ground rules forimplementing a toolkit in the subscriber identity module, and forenabling operators to create their own specific applicationsindependently of the mobile terminal used, provided that the terminal iscompatible with GSM Recommendation 11.14 phase 2+. Furthermore, to makeit possible to dialog with and to use the toolkit, GSM Recommendation11.11 phase 2+ specifies the mechanisms that make the two portions (themobile terminal and the subscriber identity module) interoperable. Inother words, the SIMs may have commands available that it can haveexecuted by the terminal.

For additional explanation on SIMs operation and protocol, please referto ETSI publications prepared by various ETSI workgroups: GSM 02.19Digital cellular telecommunications system (Phase 2+), SubscriberIdentity Module Application Programming Interface (SIM API), Servicedescription; Stage 1; GSM 02.48 Digital cellular telecommunicationssystem (Phase 2+), Security mechanisms for the SIM application toolkit;Stage 1; GSM 03.19 Subscriber Identity Module Application ProgrammingInterface (SIM API); SIM API for java Card(™), Stage 2; GSM 03.48Digital cellular telecommunications system (Phase 2+), SecurityMechanisms for the SIM application toolkit; Stage 2; GSM 11.11 Digitalcellular telecommunications system (Phase 2); Specification of theSubscriber Identity Module—Mobile Equipment (SIM—ME) interface; (GSM11.11); GSM 11.14: Specification of the SIM application toolkit for theSubscriber Identity Module—Mobile Equipment (SIM—ME) interface; WAP WIMWireless Application Protocol Identity Module Specification, available(for free) at www.wapforum.org; 3G TS 21.111 Version 3.0.0, USIM and ICCard Requirements; entitled Removable User Identity Module (R-UIM) forSpread Spectrum Systems (3GPP2 C.S0023) of Dec. 9, 1999; CDMADevelopment Group Document #43, Smart Card Stage I Description, Version1.1, May 22, 1996; GSM 02.17—Subscriber Identity Module (SIM);Functional Characteristics; 3GPP 22.038—SIM Application Toolkit (SAT),Stage 1; 3GPP 22.112—USIM Toolkit Interpreter Stage 1; 3GPP31.102—Characteristics of the USIM Application; 3GPP 31.111—USIMApplication Toolkit (USAT); 3GPP 31.113—USAT Interpreter Byte Codes;3GPP 31.131—C API for the USIM Application Toolkit; 3GPP 34.131—TestSpecification for the C SIM API; SCP 101.220 Integrated Circuit Cards(ICC); ETSI Numbering System for Telecommunication; ApplicationProviders (AID); SCP 102.221 Smart Cards; UICC—Terminal Interface;Physical and Logical Characteristics; SCP 102.222 Integrated CircuitCards (ICC); Administrative Commands for TelecommunicationsApplications; SCP 102.230 Smart Cards; UICC—Terminal interface;Physical, Electrical and Logical Test Specifications; SCP 102.223—SmartCards; Card Application Toolkit (CAT); SCP 102.224 Security mechanismsfor the Card Application Toolkit: Functional requirements; SCO102.225—Secured packet structure for UICC applications; SCP102.226—Remote APDU Structure for UICC based Applications; SCP102.240—UICC Application Programming Interface, and all related text,which is hereby incorporated by reference.

While the SIMs are useful for expanding the functionality of the mobiledevices, conventional SIMs are useful for converting the mobile deviceinto a transaction device useful in completing transactions. The presentinvention solves this problem by providing a RF module configured tocommunicate with a mobile device microprocessor using connectorscontained on the mobile device. For example, RF module may be configuredto fit within a SIM slot and mate with a mobile device, SIM connectors.

FIG. 18 depicts an exemplary alternate embodiment of RF module 20including electrical connectors 1802 configured to communicate with, andbe compatible with, conventional SIM connectors on a mobile device, suchas, cell phone 300. RF module 20 of FIG. 18 may have similar descriptionas module 300. However, in this instance RF module 20 includeselectrical connectors 1802 which may be in communication with the moduleprotocol/sequence controller 208. The connectors 1802 may additionallyplace the RF module protocol/sequence controller 208 in communicationwith the mobile device microprocessor (e.g., cell phone microprocessor1702), for transmitting information thereto. Notably, the module 20 maybe manufactured and provided to the end user using any of the methodsdescribed herein, for example, by using the methods described in FIGS. 8and 10.

FIG. 19 depicts the module 20 including connectors 1802 placed inphysical and logical communication with the electrical connectors 1902of a mobile device, such as, cell phone 300. As shown, the electricalconnectors 1802 are placed in contact with the connectors 1902 so thatinformation may be communicated between the RF module 20 and themicroprocessor 1702. As described more fully below, the cell phone 300in communication with RF module 20 may be converted into a RFtransaction device for completing a RF transaction.

FIG. 20 illustrates an exemplary transaction processing method using theRF module placed in physical and logical communication with a mobiledevice microprocessor as described above. FIG. 20 is best understoodwith reference to FIG. 1, FIG. 6, and FIG. 21 described below. Asillustrated, the transaction device 102 is a mobile device, such as forexample, mobile phone 300, that is configured to process a transactionusing a RF module 20 in physical and logical communication with themicroprocessor 1702 of the mobile device 300. The RF module 20 isprovided to the end user using any of the methods described herein. Inone example, the RF module 20 is provided integral to the mobile devicehousing and in physical and logical communication with themicroprocessor 1702. In this way, the RF module 20 may be included inthe mobile device when the device is manufactured. In a separateexample, the RF module 20 is provided to the end user independently ofthe mobile device. The RF module 20 is placed in communication with themobile device microprocessor using electrical connectors.

With brief reference to FIGS. 6 and 21, the functional components of anexemplary RFID reader 104 is described. As shown, RFID reader 104 mayinclude an antenna 2104 for providing an interrogation signal from RFIDreader 104 to the RF module 20 antenna 204. RFID reader 104 antenna maybe in communication with a reader transponder 2114. In one exemplaryembodiment, transponder 2114 may be a 13.56 MHz transponder compliantwith the ISO/IEC 14443 standard, and antenna 2104 may be of the 13 MHzvariety. The transponder 2114 may be in communication with amodulator/demodulator 2106 configured to receive the signal fromtransponder 2114 and configured to modulate the signal into a formatreadable by any later connected circuitry. Further,modulator/demodulator 2106 may be configured to format (e.g.,demodulate) a signal received from the later connected circuitry in aformat compatible with transponder 2114 for transmitting to RF module 20via antenna 2104. For example, where transponder 2114 is of the 13.56MHz variety, modulator/demodulator 2106 may be ISO/IEC 14443-2compliant.

Modulator/demodulator 2106 may be coupled to a protocol/sequencecontroller 2108 for facilitating control of the authentication of thesignal provided by RF module 20, and for facilitating the formatting ofthe data received from RF module 20 in a format compatible with, forexample, a merchant POS 110. In this regard, protocol/sequencecontroller 2108 may be any suitable digital or logic driven circuitrycapable of facilitating determination of the sequence of operation forthe RFID reader 104 inner-circuitry. For example, protocol/sequencecontroller 2108 may be configured to determine whether the signalprovided by the RF module 20 is authenticated, and thereby providing tothe RF module 20 account number to the merchant POS 110.

Protocol/sequence controller 2108 may be further in communication withauthentication circuitry 2110 for facilitating authentication of thesignal provided by RF module 20. Authentication circuitry 2110 may befurther in communication with a non-volatile secure memory database2112. Secure memory database 212 may be of similar description asdatabase 212 described above. Authentication circuitry 2110 mayauthenticate the signal provided by RF module 20 by association of thesignal to authentication keys stored on database 2112. Encryptioncircuitry 2116 may use keys stored on database 2112 to performencryption and/or decryption of signals sent to or from the RF module20.

Returning now to FIG. 20, a typical transaction in accordance with thisinvention is described. The transaction may begin when an end userpresents the transaction device (e.g., 300) including a RF module 20 fortransaction processing (step 2002). The RFID reader 104 provides aninterrogation signal to the RF module 20 for activating the RF module 20for transaction processing (step 2004). The RF module 20 receives theinterrogation signal (step 2006) and the RF module 20 and the RFIDreader 104 engage in mutual authentication to determine if each is avalid device for operation on system 100 (step 2008).

FIG. 22 is a flowchart of an exemplary authentication process inaccordance with the present invention. The authentication process isdepicted as one-sided. That is, the flowchart depicts the process of theRFID reader 104 authenticating the RF module 20, although similar stepsmay be followed in the instance that RF module 20 authenticates RFIDreader 104. In some embodiments, the RF module 20 and the RFID reader104 may engage in mutual authentication. In this context, “mutualauthentication” may mean that operation of the system 100 may not takeplace until RF module authenticates the signal from RFID reader 104, andRFID reader 104 authenticates the signal from RF module 20.

As noted, database 2112 may store security keys for encrypting ordecrypting signals received from RF module 20. In an exemplaryauthentication process, where RFID reader 104 is authenticating RFmodule 20, RFID reader 104 may provide an interrogation signal to RFmodule 20 (see step 2002 of FIG. 20). The interrogation signal mayinclude a random code generated by the RFID reader authenticationcircuit 2110, which is provided to the RF module 20, and which isencrypted using a unique encryption key corresponding to, for example, aRF module 20 unique identification code. In a typical scenario, theprotocol/sequence controller 2108 may provide a command to activate theauthentication circuitry 2110. Authentication circuitry 2110 may providefrom database 2112 an interrogation signal including a random number asa part of the authentication code generated for each authenticationsignal. The authentication code may be an alphanumeric code which isrecognizable (e.g., readable) by the RFID reader 104 and the RF module20. The authentication code may be provided to the RF module 20 viaantenna 2104 (step 2202).

RF module 20 receives the authentication code (step 2204). Theinterrogation signal including the authorization code may be received atthe RF module antenna 204. The authorization code may be provided to themodulator/demodulator circuit 206 where the signal may be demodulatedprior to providing the signal to protocol/sequence controller 208.Protocol/sequence controller 208 may recognize the interrogation signalas a request for authentication of the RF module 20 (step 2206), andprovide the authentication code to authentication circuit 210.Authentication circuit 210 or protocol/sequence controller 208 mayretrieve an encryption key from database 212 and authentication circuit210 may encrypt the authentication code using the retrieved encryptionkey (step 2208). RF module 20 may then provide the encryptedauthentication code to the RFID reader 104 for verification (step 2210).The encrypted authentication code may be provided to the RFID reader 104via RF module modulator/demodulator circuit 206, transponder 214, andantenna 202.

RFID reader 104 may then receive the encrypted authentication code anddecryption it (step 2212). That is, the encrypted authentication codemay be received at antenna 2104 and transponder 2114, and provided toauthentication circuit 2110. Authentication circuit 2110 may be provideda security authentication key (e.g., transponder system decryption key)from database 2112. The authentication circuit 2110 may use theauthentication key to decrypt (e.g., unlock) the encrypted authorizationcode. The authentication key may be provided to the authenticationcircuit 2110 based on the RF module 20 unique identification code. Forexample, the encrypted authentication code may be provided along withthe unique RF module 20 identification code. The authentication circuit2110 may receive the RF module 20 unique identification code andretrieve from the database 2112 a transponder system decryption keycorrelative to the unique RF module 20 identification code for use indecrypting the encrypted authentication code.

Once the authentication code is decrypted (step 2212), the decryptedauthentication code is compared to the authentication code provided bythe RFID reader 104 to verify its authenticity (step 2214). If thedecrypted authorization code is not readable (e.g., recognizable) by theauthentication circuit 2110, the RF module 20 is deemed to beunauthorized (e.g., unverified) (step 2216) and the operation of system100 is terminated (step 2218). Contrarily, if the decryptedauthorization code is recognizable (e.g., verified) by the RF module 20,the decrypted authorization code is deemed to be verified orauthenticated (step 2220), if so, the transaction is allowed to proceed(step 2222). In one particular embodiment, the preceding transaction maymean that the RF module 20 may authenticate the RFID reader 104,although, it should be apparent that the RFID reader 104 mayauthenticate the RF module 20 prior to the RF module 20 authenticatingthe RFID reader 104.

With return reference now to FIG. 20, upon successful mutualauthentication, the RF module 20 transfers to the RFID reader 104 suchdata as is necessary to process a transaction request (“user accountdata”) (step 2210).

The RFID reader 104 receives the user account data at the antenna 2104,and provides the data to the POS interface 2120 (step 2012). In oneexemplary embodiment, the RFID reader authentication circuit 2110 mayreceive the data and provide the data to the RFID reader interface 2120.The RFID reader interface 2120 may then receive the data and convert thedata to a merchant POS 110 recognizable format for providing to themerchant system 130. In an exemplary embodiment, the user account datais provided to the RFID reader 104 in magnetic stripe format. In yetanother embodiment, the RFID reader 104 provides the user account datato the merchant POS 110 in magnetic stripe format.

The merchant system 130 may receive the user account data and use thedata to form a transaction request (step 2014). The transaction requestmay include the user account data and any information related to thetransaction. The merchant system 130 may provide the transaction requestto a user account issuer for processing under business as usualstandards (step 2016). Notably, the transaction applications forprocessing the authentication signal and providing the user account datamay be stored in a transaction application on for example, in thedatabase 212 for use by the authentication circuit 210.

In one exemplary embodiment of the invention, the transaction device 102(e.g., mobile phone 300) may include a USB interface 2122 incommunication with the protocol/sequence controller 2108. In thisexemplary embodiment, the USB interface 2122 may be a RS22 serial datainterface. Alternatively, the RFID reader 104 may include a serialinterface such as, for example, a RS232 interface in communication withthe protocol/sequence controller 2108. In either embodiment, theinterface may be in communication with the protocol/sequence controller2108 for providing user account data from the RF module 20 fortransaction processing, using, for example, the transaction processingmethod of FIG. 20.

To facilitate the user account data transfer from the RF module 20 tothe interface 2122, the mobile phone 300 may be equipped with a USBinterface 304 (shown in FIG. 13) or the like. The mobile device USBinterface 304 may be included in the mobile device 300, when the phone300 is manufactured and prior to providing the phone to the end user.The mobile device USB interface 304 may be placed in communication withthe USB interface 2122. In that regard, USB interface 304 may becompatible with USB interface 2122, such that the data received from themobile phone 300 is recognizable by the RFID reader 104.

In a typical embodiment, the RF module 20 is in physical and logicalcommunication with the mobile device (e.g., mobile phone 300)microprocessor 1702, for transmitting user account data from the RFmodule 20 to the RFID reader 104. The module protocol/sequencecontroller 208 may retrieve the user account data from the moduledatabase 212 and provide the data to the microprocessor 1702. Themicroprocessor 1702 may then provide the user account data to the USBinterface 304 for providing to the RFID reader USB interface 2122. USBinterface 2122 may receive the user account data and provide the data toa merchant POS 110 for processing as described above.

It should be noted that although the present invention is described withrespect to the mobile device USB being connected to a USB of a RFIDreader 104, the invention is not so limited. For example, the mobiledevice USB may be connected to a similar port (e.g., USB port) includedon a kiosk, or personal computer, stand alone computing device, or thelike. In this case, the user account data may be transmitted from themobile device to the kiosk or other computer and to an offline or onlineaccount issuer or merchant system for transaction processing via an openor closed network. In this instance, an “open” network is onesusceptible to eavesdropping.

Placing the RF module 20 in physical and logical communication has theadvantage in that the RF module 20 may be powered by a power source ofthe mobile device. That is, the RF module 20 may share a similar powersource as does the functional components of the mobile device. Anotheradvantage is that the mobile device's user interface may be used toverify secondary information from the end user.

For example, the RF module 20 may need to be switched on prior to usefor transaction completion. In this case, the end user may use themobile device user interface (e.g., keyboard 306) to enter aalphanumeric code for powering the RF module 20. The alphanumeric codemay be received by the microprocessor 1702 and forwarded to the protocolsequence controller 2108 to commence a transaction using the RF module20. In another instance, the end user may provide an alphanumeric codein response to a request from the RFID reader 104 for furtherauthentication of the end user's identity. For example, the RFID reader104 may send a message to the RF module 20 that a secondary form ofidentification, such as a personal identification number (PIN), isrequired before a transaction may proceed. The RFID readerauthentication circuit 2110 may receive a signal from the RF module 20and recognize that the end user's identity may need to be verified usinga PIN. The authentication circuit 2110 may then provide the RF module 20with a request for the end user to provide the PIN before the RF moduleprovides the user account data to the RFID reader 104.

In one exemplary embodiment, the reader 104 may provide the request fora PIN to the RF module 20 at antenna 204. The RF module transponder 214may receive the request and provide the request for PIN to theprotocol/sequence controller 208. The protocol/sequence controller 208may provide the request to the mobile phone microprocessor 1702, and themicroprocessor 1702 may send a prompt to the mobile device display unit,such as the display unit 308 of mobile phone 300. The display unit 308may be any conventional display units that are used with mobile personalcommunication devices, such as, mobile phones, PDAs, personal computersor the like. Suitable display units which may be used with the inventioninclude a liquid crystal display unit (LCD), image display device, orthe like. The display unit may be any display unit capable of displayingmessages to the end user.

The end user may then be permitted to input the PIN using the keypaduser interface 306. The PIN may be provided to the microprocessor 1702,which may provide the PIN to the module protocol/sequence controller208. The protocol/sequence controller 208 may provide the PIN to themodule authentication circuit 210, which may retrieve from the database212 (or from encryption circuit 216) a PIN verification key and use theverification key to authenticate the PIN. The authentication circuit 210may use any authentication method as is found in the art, or disclosedherein to verify the PIN. In one exemplary embodiment, theauthentication circuit 210 may compare the PIN provided by the end userto the PIN verification key using any comparison method permitting theauthenticity of the PIN to be verified.

Alternatively, the RF module protocol/sequence controller 208 mayprovide the PIN to the RFID reader 104 for authentication. The RFIDreader authentication circuit 210 may receive the PIN and verify the PINin a similar manner as is discussed with respect to the RF module 20.

Notably, the method by which the end user provides the PIN to themicroprocessor 1702 may vary. For example, the user interface mayinclude a touch screen display and a stylus as is found in the art.Additionally, the secondary form of identification may be provided usingbiometric or voice recognition technology. The mobile device may receivethe biometric or voice data and convert it into data recognizable by theRF module protocol/sequence controller 208 for verification using themethods discussed above.

To facilitate the above transaction and authentication methods, the RFmodule 20 may be “personalized” to include user account data,encryption, decryption keys, and the like. The information provided tothe RF module 20 during the personalization process may be used toenable the RF module 20 to process a RF transaction. Such informationmay be stored in a “personalization file,” provided to the RF module 20and stored on module database 212.

FIG. 23 illustrates an exemplary personalization system 2300, and FIGS.24A–B depict an exemplary personalization method, useful with thepresent invention. The personalization system 2300 includes atransaction device 102 in communication with a mobile device accountissuer 2304, which is in further communication with a RF module accountissuer 2306, including a personalization unit 2302 for personalizing theRF module 20.

The transaction device 102 may be in communication with the mobiledevice account issuer 2304 via communications using the transactiondevice 102 ordinary communication method. Alternatively, the transactiondevice 102 may be in communication with the mobile device account issuer2304 using a mobile device USB connector (e.g., USB connector 304) incommunication with a kiosk, stand alone computer, or online computer orthe like, in communication with the mobile device account issuer 2304.

To begin personalization, the end user may, for example, contact amobile device issuer 2304 using a key pad 306 and the mobile device'sordinary method of communication (step 2402). The end user notifies themobile device account issuer 2304 that a RF module 20 is to bepersonalized (step 2404). In this context, a mobile account issuer 2304may include any service provider for mobile phones. Exemplary providersmay include AT&T, Southern Bell, Cox Communications, Sprint, Verizon,Cingular, T-Mobile, Nextel, etc. The ordinary method of communicationmay be any suitable data transmission method as is used by the exemplaryproviders.

The mobile device account issuer 2034 may then establish communicationwith the RF module account issuer 2306 for transmitting personalizationor authentication information thereto (step 2406). The mobile accountissuer 2304 may facilitate direct or indirect communication between theRF module account provider 2306 and the mobile device 102 or RF module20. The mobile device account provider 2304 may, for example, facilitate“direct” communication by facilitating communication between mobiledevice 102 and the RF module 20 so that information may be directlytransmitted between the device 102 and the RF module account provider2306. Alternatively, the mobile device account issuer 2304 may establish“indirect” communications by facilitating communication between themobile device 102 and the RF module account issuer 2306, via third partyor via the mobile account issuer system 2304. In either instance, the RFmodule account issuer 2306 is placed in communication with the RF module20 (via mobile device 102) for authentication and personalization.

Personalization unit 2302, which may be included in RF module accountissuer system 2306, may be placed in communication with a mobile phone300 (step 2408).

Personalization unit 2302 may be in communication with the RF module 20while in physical and logical communication with the mobile device 300for populating RF module database 212 with the security keys andidentifiers for facilitating authentication of the unique RFID reader104 identifier. Personalization unit 2302 may also populate (e.g.,inject) the encrypted RF module 20 account number into RF moduledatabase 214 for later providing to an authenticated RFID reader 104.

In one exemplary embodiment, personalization unit 2302 may include anystandard computing system as described above. For example,personalization unit 2302 may include a standard personal computercontaining a hardware security module operable using any conventionalgraphic user interface.

Personalization unit 2302 and RF module 20 may be configured to transmita RF module personalization file to RF module 20 using the mobile deviceordinary transmission method (step 2410). The personalization unit 2302may create as a part of the personalization file, a unique identifierfor providing to the RF module 20. The identifier is unique in that oneidentifier may be given only to a single fob. That is, no other RFmodule may have that same identifier. The RF module 20 may then beconfigured and loaded with that identifier. That is, the RF moduleunique identifier may be provided to the module protocol/sequencecontroller 208 which may provide the unique identifier to the database212. The personalization file may be provided as encrypted data althoughencryption is not required.

The encrypted RF module 20 personalization file may be populated into RFmodule 20 (step 2412). Mobile phone 300 may receive the personalizationfile at mobile phone antenna 1708, demodulate the information atmodulator/demodulator 1706, receive the information at microprocessor1702, and forward the information to RF module 20. Microprocessor 1702may provide the personalization file to the RF module 20protocol/sequence controller 208 and inject the encrypted account intoRF module database 212.

Once the personalization file is populated into the RF module 20, thepopulated information is irreversibly locked to prevent alteration,unauthorized reading and/or unauthorized access (step 2414).Personalization unit 2302 may then create a log of the personalizationfile information for later access and analysis by the personalizationunit 2302 user (step 2416).

It should be noted that in the event the personalization unit 2302process is compromised or interrupted, the personalization system maysend a security alert to the user and the personalization process may beaborted. On the other hand, where no such compromising or interruptionexists, the personalization system may be prepared to beginpersonalization of subsequent RF modules.

FIGS. 25A–B illustrate another exemplary embodiment of a personalizationprocess which may be used to personalize RF module 20, where the RFmodule 20 may be personalized for the first time. By way of example, themethod discusses a RF module 20 placed in communication with apersonalization unit 2302 via a transaction device USB connector, suchas, USB 304 (step 2502). Once connected, personalization unit 2302 mayestablish communications with the RF module 20 (step 2504). If the RFmodule 20 is being personalized for the first time (step 2506) the RFmodule 20 and the personalization unit 2302 may engage in mutualauthentication as described above with respect to FIGS. 24A–B (step2508). After the mutual authentication is complete, personalization unit2302 may verify that RF module 20 is properly manufactured or configuredto operate within system 100 (step 2510). The verification may includeevaluating the operation of the RF module 20 by determining if the RFIDreader will accept predetermined default settings. That is, thepersonalization unit 2302 may then provide the RF module 20 a set ofdefault settings and determine if the RF module 20 accepts thosesettings. If RF module 20 does not accept the default settings,personalization unit 2302 may abort the personalization process (step2512). Otherwise the personalization unit 2302 provides thepersonalization file to the RF module 20 for storing on database 212(step 2511).

If the personalization unit 2302 determines that the personalizationprocess is not the first personalization process undertaken by the RFmodule 20 (step 2506), personalization unit 2302 and RF module 20 mayengage in a mutual authentication process using the existing securitykeys already stored on RF module 20 (step 2514). If authentication isunsuccessful (step 2516), the personalization system may abort thepersonalization process (step 2518).

Where the personalization unit 2302 and the RF module 20 successfullymutually authenticate (step 2520), the personalization unit 2302 mayupdate the RF module 20 security keys (step 2522). Updating the securitykeys may take place at any time as determined by a system RF moduleaccount provider 2306. The updating may take place as part of a routinemaintenance or merely to install current security key data. The updatingmay be performed by downloading firmware into RF module 20. In the eventthat the personalization system determines that the RF module 20 isundergoing an initial personalization, the firmware may be loaded intothe RF module 20 for the first time. In this context, “firmware” mayinclude any file, which enables the RF module 20 or RFID reader 104 tooperate under system 100 guidelines. For example, such guidelines may bedirected toward the operation of RFID reader protocol/sequencecontroller 314.

Personalization unit 2302 may then determine if the personalization keys(e.g., security keys, encryption decryption keys, RF identifier, RFmodule identifier or account number, etc.) need to be updated or if theRF module 20 needs to have an initial installation of thepersonalization keys (step 2524). If so, then personalization unit 2302may download the personalization keys to the RF module database 212 asappropriate (step 2526).

The information (e.g., RF module security keys and identifiers) may bedownloaded in an encrypted format and the RF module 20 may store theinformation in the RF module database 212 as appropriate. Thepersonalization unit 2302 may then create or update a status logcataloging for later use and analysis by the personalization unit 2302user (step 2528). Upon updating the status log, the personalizationprocess may be terminated.

The preceding detailed description of exemplary embodiments of theinvention makes reference to the accompanying drawings, which show theexemplary embodiment by way of illustration. While these exemplaryembodiments are described in sufficient detail to enable those skilledin the art to practice the invention, it should be understood that otherembodiments may be realized and that logical and mechanical changes maybe made without departing from the spirit and scope of the invention.Thus, the preceding detailed description is presented for purposes ofillustration only and not of limitation, and the scope of the inventionis defined solely by the appended claims and their legal equivalentswhen properly read in light of the preceding description. For example,the steps recited in any of the method or process claims may be executedin any order and are not limited to the order presented. In addition,although the present description illustrates the invention as embodiedin a card, key fob, or cellular phone, the invention is not so limited.That is, the present invention contemplates the incorporation of theinventive technology into a form factor presentable by hand.

1. A method for facilitating remote configuration of a radio frequency(RF) module to enable the module to complete financial transactions viaRF using a financial transaction account associated with an RF moduleaccount issuer, the method comprising: a. providing the RF module, whichis configured for use with a mobile device comprising a mobile devicemicroprocessor, and configured to be in physical and logicalcommunication with the mobile device microprocessor; b. facilitatingmutual authentication between an RF module personalization system andthe RF module; and c. transmitting personalization data from the RFmodule account issuer to the RF module via the mobile devicemicroprocessor to enable the RF module to complete financialtransactions via RF, wherein the transmission of the personalizationdata is performed by the RF module personalization system, and whereinthe personalization data comprises financial transaction account dataand an encryption key, the account data comprising an account number andan account expiration date.
 2. A method of claim 1, further comprisingproviding the RE module with an authentication key prior to providingthe RF module to the mobile device.
 3. A method of claim 1, furthercomprising communicating with the RF module via a mobile device accountissuer to facilitate mutual authentication between the RF modulepersonalization system and the RF module.
 4. A method of claim 1,further comprising communicating with the RF module to supply thepersonalization data via the mobile device subsequent to communicatingwith a mobile device account issuer.
 5. A method of claim 4, furthercomprising verifying that the RF module is valid for personalization bythe RF module personalization system.
 6. A method of claim 1, furthercomprising providing the personalization data to the RF module via amobile device account issuer.
 7. A method of claim 1, further comprisingproviding the personalization data to the RF module through directcommunication.
 8. A method of claim 1, further comprising providing thepersonalization data to the RF module via a mobile device universalserial bus (USB), the mobile device USB being in communication with theRF module personalization system and with the mobile devicemicroprocessor.
 9. A computer-readable storage medium containing a setof instructions for a general purpose computer configured to: a.facilitate mutual authentication between an RF module personalizationsystem and an RF module, the RF module is configured for use with amobile device comprising a mobile device microprocessor, and configuredto be in physical and logical communication with the mobile devicemicroprocessor; and b. transmit personalization data from the RF moduleaccount issuer to the RF module via the mobile device microprocessor toenable the RF module to complete financial transactions via RF, whereinthe transmission of the personalization data is performed by the RFmodule personalization system, and wherein the personalization datacomprises financial transaction account data and an encryption key, theaccount data comprising an account number and an account expirationdate.
 10. A system for remotely configuring an RF module radio frequency(RF) module to enable the module to complete financial transactions viaRF using a financial transaction account associated with an RF moduleaccount issuer, the system comprising: a. the RF module, which isconfigured for use with a mobile device comprising a mobile devicemicroprocessor, and configured to be in physical and logicalcommunication with the mobile device microprocessor, the RF modulecomprising an RF module device database configured to storepersonalization data, the mobile device microprocessor configured toprovide the personalization data to the RF module database for storage;b. a mobile device account issuer communication interface configured toenable communication between a mobile device account issuer and the RFmodule via the mobile device microprocessor, and c. an RF module accountissuer system comprising an RF module personalization system, the RFmodule personalization system being configured to transmit thepersonalization data from the RF module account issuer system to the RFmodule, wherein the personalization data comprises financial transactionaccount data and an encryption key, the account data comprising anaccount number and an account expiration date.
 11. A system of claim 10,wherein the personalization data is provided to the RF module via themobile device account issuer, the mobile device account issuer beingconfigured to communicate with the RF module account issuer forreceiving the personalization data.
 12. A system of claim 11, whereinthe mobile device includes a universal serial bus (USB) connector incommunication with the RF module via the mobile device microprocessorfor providing the personalization data to the RF module.
 13. A system ofclaim 10, wherein the personalization data is provided to the RF modulesubsequent to the mobile device communicating to the mobile accountissuer that a RF module is to be personalized.